04/08/2024 - 10/08/2024

06/08/2024 15:19

Followed these steps to mount the SSD to a XFS (high performance) file system:

1. Create Mount

sudo mkfs.xfs /dev/nvme0n1
sudo mkdir /data/ssd
sudo mount /dev/nvme0n1 /data/ssd

sudo mkfs.xfs /dev/nvme0n1
sudo mkdir /data/ssd
sudo mount /dev/nvme0n1 /data/ssd

2. Verify Mount

df -h

df -h

**3. Update /ect/fstab for persistent mount on boot **

i) Get UUID:

sudo blkid /dev/nvme0n1

sudo blkid /dev/nvme0n1

ii) Note output, for example:

/dev/nvme0n1: UUID="002e991c-d707-4e80-adb3-709087f45151" TYPE="xfs"

/dev/nvme0n1: UUID="002e991c-d707-4e80-adb3-709087f45151" TYPE="xfs"

iii) Add line to /ect/fstab

sudo nano /etc/fstab
UUID=002e991c-d707-4e80-adb3-709087f45151 /data/ssd xfs defaults 0 0

sudo nano /etc/fstab
UUID=002e991c-d707-4e80-adb3-709087f45151 /data/ssd xfs defaults 0 0

To save and exit, Ctrl+X then Y then Enter.

Notes:

Every test is done with one crate enabled, logging BUF001
"AMC13 Lagged behind?" just means I visually percieved the event rate suffer with the logger on
"Percieved Data Rate" is just the rate I saw updating on the midas webpage
"SSD" just means I wrote to /data/ssd/midas_data_files where I have an SSD mounted
"HDD" just means I wrote to /home/installation_testing/online where I have an HDD mounted
(?) Indicates the value jumped around a lot
~ Indicates the data rate jumped around a bit, but this was a percieved average

Waveform Length	Internal Trigger Period (μs)	Drive Type	Perceived Data Rate (MB/s)	Expected Data Rate (MB/s)	AMC13 Lagged behind?
4800	110	SSD	~280(?)	~450	Yes
2400	110	SSD	~200(?)	~220	Yes
1600	110	SSD	~150	~150	No
1600	110	HDD	~150	~150	No
9000	500	SSD	~180	~180	No
9000	500	HDD	~180	~180	No
12000	500	SSD	~240	~240	No
12000	500	HDD	~240	~240	Yes (barely)
15000	500	SSD	~240	~300	Yes
15000	500	HDD	~240	~300	Yes